Skip to main content

ScrollView How To's

How to's for the ScrollView guide.

How to Use ScrollView?​

How to Use ScrollView?​

The following steps should be followed to add and effectively use the ScrollView object on a form.

Add the ScrollView Object to the Form​

  1. Open the form design screen
  2. Go to the Toolbox panel
  3. Locate the ScrollView object
  4. Add the object to the form using drag / drop

The ScrollView appears on the form as a container area.

Add Content Objects into the ScrollView​

Drag and place form objects such as:

  • TextBox
  • ComboBox
  • DataGrid
  • ListBox
  • Panel, Collapse, etc.

into the ScrollView area.

All objects added inside the ScrollView become part of the scrollable area.

Configure the Size​

  • The height of the ScrollView is adjusted according to the form design
  • If the content exceeds this height, a scroll bar is automatically generated

As a result:

  • The entire form does not extend vertically
  • Only the ScrollView area becomes scrollable

Run and Test​

  1. Run / Publish the project
  2. Open the form in the web interface
  3. Verify that the content inside the ScrollView can be scrolled

Example Usage​

Scenario:
A long application form contains user information, address details, and additional fields.

Solution:
By placing all fields inside a ScrollView:

  • The screen remains clean and compact
  • The user can access all fields by scrolling down

Tips​

  • ScrollView is especially recommended for mobile forms
  • Nested ScrollView usage is not recommended from a UX perspective
  • It is highly effective when used together with Collapse or TabMenu

How to Use Client Enabled?​

What is Client Enabled?​

Client Enabled is a property that defines whether a form control is active (enabled) on the client side when the form is first loaded.
If it is set to True, the control is immediately usable by the user.
If it is set to False, the control is disabled and cannot be interacted with until a specific condition or rule activates it.

This property is especially useful for controlling the user’s interaction flow and applying dynamic behaviors using the Rule Manager.

What Does It Do?​

The property allows developers to:

  • Control when a form control becomes interactive.
  • Prevent users from entering or changing data until prerequisites are met.
  • Dynamically enable or disable controls based on user input or logic.

Example Scenario — Conditional Activation​

Scenario:
A form contains a checkbox called “I Accept Terms” and a text field called “Signature.”
The goal is to make the “Signature” field inactive until the user checks “I Accept Terms.”

Steps to Implement:​

  1. Select the “Signature” field in the form editor.

  2. In the Properties panel, find the Client Enabled field.

  3. Set the value to False — the field will now be disabled by default when the form loads.

  4. Open the Rule Manager.

  5. Add a new rule:

    Condition:

Action:

  1. Save and publish the form.

Result:​

  • When the form loads, the “Signature” field is disabled.
  • Once the user checks “I Accept Terms,” the field automatically becomes active and editable.

Behavior Summary​

Property StateDescription
TrueThe control is active and ready for user interaction when the form loads.
FalseThe control is disabled at load time and can be enabled dynamically via rules or code.

Notes & Best Practices​

  • Use the Client Enabled property to manage client-side interactivity without requiring server actions.
  • Combine it with Rule Manager to define when and how controls become active.
  • Remember: if server enablement is disabled, the client cannot enable the control even if Client Enabled is set to True.
  • By default, this property is set to True (active).

Summary​

Client Enabled improves form usability by letting developers control when and how users interact with form controls.
It is essential for creating responsive, condition-based form experiences where user actions dynamically change the form’s state.

What Is ScrollView?​

What Is ScrollView?​

ScrollView is a container object that enables vertical or horizontal scrolling of form content when the objects on the form exceed the screen size.

With this object, even if a form contains many fields or large content, a smooth navigation experience is provided to the user without breaking the screen layout.

ScrollView is commonly used in:

  • Long forms
  • Mobile or small-screen layouts
  • Dynamically growing content

What Is It Used For?​

  • Collects form content in a single area
  • Provides scrolling for overflowing content
  • Prevents the entire form from extending vertically
  • Improves user experience (UX)

Usage Scenarios​

  • Forms containing a large number of fields
  • Mobile-friendly form designs
  • Objects that generate long content such as DataGrid or ListBox
  • Overflowing areas inside Collapse or TabMenu

Notes​

  • ScrollView does not store data by itself; it is only a content container
  • Any type of form object can be added inside it
  • Scroll bars are generated automatically based on content size